Building the model of the Order Handling process

In this lesson, you will build the model of the Order Handling process.

1. If the OrderHandling process is not open already, expand ClipsAndTacksF1 >Processes > OrderHandling, and then double-click OrderHandling.
   
   Tip: The canvas is currently much larger than the area visible within the window. From the toolbar, click the Resize Diagram icon and choose from the options to resize the process diagram. To reduce the width of the canvas, use the Decrease Horizontal Space icon . To reduce the height of the canvas, use the Decrease Vertical Space icon .
2. On the palette, click Business Rules Task and then click the canvas. Rename the local business rules task to Check Order Handling Policy for Automatic Approval. You can resize the task to fully display the text if you want.
   Tip: You can also drag elements from the palette to the canvas.

   Add new elements to the right of the previously added item. An image with all the elements in the process is included in the Connecting the tasks and associating data section.

   

3. On the palette, click Gateways to expand it. Click Simple Decision, and then click the canvas. Rename the simple decision to Approve Without Review?
4. On the palette, click Task, and then click the canvas. Rename the task to Check Customer Account Status. The generic task icon can be used to represent any call to an automated service.
   Note: You might experience errors during this part of the tutorial because you are in the Fabric mode by default. If you do not want to experience those errors, change to the Basic mode.
   
5. Click Simple Decision, and then click the canvas to the right of the Check Customer Account Status task. Rename the simple decision to Account in Good Standing?
6. On the palette, click Merge, and then click the canvas.
   Tip: Place the merge elements on the canvas from left to right as you define them.
7. On the palette, click Human Task, and then click the canvas. Rename the human task to Review Order.
   
8. Add a simple decision called Acceptable Credit Risk? to the right of the previous item, a merge item to the canvas to the right of the Acceptable Credit Risk? simple decision, and a task called Calculate Shipping Charges to the canvas to the right of the merge item.
   
9. You can now indicate what type of task this represents. Select CalculateShippingCharges and select the Implementation tab in the Technical Attributes view. Scroll down and select Dynamic Assembler for the Implementation Type. This setting enables you to add dynamic behavior to the process.
   
10. Add a human task called Ship Order to Customer, a task called Update Order Database, and a task called Cancel Order and Send Notification to the canvas. Note: Exact spelling and capitalization is required for the Cancel Order and Send Notification task. In the integration section of this tutorial, you will associate an implementation to this task. The implementation file is supplied for you and the name must match.
11. Set the implementation types for the Check Customer Account Status, Update Order Database, and Cancel Order and Send Notification tasks to Java.
    
12. Add a Terminate node by clicking the Terminate icon on the palette and then clicking the canvas. (The Terminate icon is located under the Events group.)
13. Add a second Terminate node.